Network awareness of device location

ABSTRACT

Systems and methods for managing a network are disclosed. One method can comprise detecting a triggering event at a node. Location information of the node can be transmitted to a routing device in response to the triggering event. Location information of the node can be transmitted to a management device. The management device can be configured to control an operation of one or more of the node and the routing device in response to the location information.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/721,683 filed Dec. 20, 2012, which is hereby incorporated byreference in its entirety.

BACKGROUND

A network such as a wireless local area network can comprise one or moreaccess points (AP) to provide a means for one or more user devices tocommunicate with and/or over the network. An access point can comprise adevice that allows wireless user devices to connect to a wired networkusing Wi-Fi, Bluetooth, or related standards.

Often, a Media Access Control address (MAC address) is assigned tonetwork interfaces, such as AP's, to facilitate addressablecommunications on a physical network segment. MAC addresses can be usedfor numerous network technologies, including most IEEE 802 networktechnologies, including Ethernet. Logically, MAC addresses can be usedin the media access control protocol sub-layer of the open systemsinterconnection (OSI) reference model.

Currently, when a user device initially connects to a particular firstAP of a network, the MAC address for the AP that the user device isconnecting through is detected. The detected MAC address can betransmitted to a gateway of the network for addressing and referencingthe user device on the network. However, when the user device roams to asecond AP on the same network, the MAC address information of the secondAP may not be detected or updated. Accordingly, improvements are neededfor monitoring and locating devices connected or trying to connect tothe network.

SUMMARY

It is to be understood that both the following general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive, as claimed. Provided are methods and systemsfor providing network services to one or more user devices or clients.The methods and systems described herein, in one aspect, can determine alocation of one or more user devices connected to one or more accesspoints of a network.

In an aspect, in the OSI reference model, a virtual layer 2 connectioncan be provided to facilitate the connectivity of one or more userdevices and one or more access points of a network. In an aspect, anencapsulation of layer 2 frames over layer 3 networks enables an accesspoint to act as a layer 2 bridge between two devices, such as between aclient and a gateway. As an example, a user device can roam between theone or more access points to maintain connectivity to the same network.As a further example, the user device can have a persistent identifieror address associated therewith while connected to the network.

In an aspect, a layer 3 connection can be provided between one or moreaccess points of the network to facilitate the transmission of locationinformation to a gateway or router device of the network. As a furtherexample, a Generic Routing Encapsulation (GRE) encapsulation can be usedto transmit location information relating to one or more access pointsconnected to the user device.

In an aspect, a network gateway device and/or upstream devices canreceive the location information. As an example, the network gatewaydevice can transmit the location information in authentication andaccounting messages to a computing device such as an authentication,authorization and accounting (AAA) server. As a further example, the AAAserver can store and/or update the location information in a networksession state for the located user device when the user device movesbetween access points on the network. In an aspect, session schema cancomprise date/time, calling station identifier, called stationidentifier, Internet Protocol (IP) Address IPV4/IPV6, accountinformation, or other data points.

In an aspect, methods can comprise detecting a triggering event at anode of a network. As an example, location information relating to thenode can be transmitted to a routing device such as a network gatewaydevice in response to the triggering event. As a further example, thelocation information can be encapsulated for transmission such as by GREencapsulation. The location information can be transmitted to amanagement device such as an AAA server. As an example, the managementdevice can be configured to control an operation of one or more of thenode and the routing device in response to the location information.

In another aspect, methods can comprise receiving first locationinformation based upon a user communication with a first node of anetwork. Second location information can also be received based upon auser communication with a second node of the network. As an example, thesecond location information is received in an encapsulated format suchas GRE encapsulation. As a further example, client location data can bestored and/or updated based on the second location information.

In a further aspect, a network can comprise a first node configured tocommunicate with a user device and transmit first location informationto a routing device. The first location information can be transmittedin a first format. As an example, a second node of the network can beconfigured to communicate with the user device and transmit secondlocation information to the routing device. The second locationinformation can be transmitted in a second format. As a further example,the user device can be addressed by a persistent identifier whencommunicating with one or more of the first node and the second node.

Additional advantages will be set forth in part in the description whichfollows or may be learned by practice. The advantages will be realizedand attained by means of the elements and combinations particularlypointed out in the appended claims. It is to be understood that both theforegoing general description and the following detailed description areexemplary and explanatory only and are not restrictive, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments and together with thedescription, serve to explain the principles of the methods and systems:

FIG. 1 is a block diagram of an exemplary system and network;

FIG. 2 is a block diagram of an exemplary computing device;

FIG. 3 is a diagram of an exemplary system and network;

FIG. 4 is a diagram of an exemplary system and network;

FIG. 5 is a flow chart of an exemplary method;

FIG. 6 is a flow chart of an exemplary method; and

FIG. 7 is a flow chart of an exemplary method.

DETAILED DESCRIPTION

Before the present methods and systems are disclosed and described, itis to be understood that the methods and systems are not limited tospecific methods, specific components, or to particular implementations.It is also to be understood that the terminology used herein is for thepurpose of describing particular embodiments only and is not intended tobe limiting.

As used in the specification and the appended claims, the singular forms“a,” “an,” and “the” include plural referents unless the context clearlydictates otherwise. Ranges may be expressed herein as from “about” oneparticular value, and/or to “about” another particular value. When sucha range is expressed, another embodiment includes from the oneparticular value and/or to the other particular value. Similarly, whenvalues are expressed as approximations, by use of the antecedent“about,” it will be understood that the particular value forms anotherembodiment. It will be further understood that the endpoints of each ofthe ranges are significant both in relation to the other endpoint, andindependently of the other endpoint.

“Optional” or “optionally” means that the subsequently described eventor circumstance may or may not occur, and that the description includesinstances where said event or circumstance occurs and instances where itdoes not.

Throughout the description and claims of this specification, the word“comprise” and variations of the word, such as “comprising” and“comprises,” means “including but not limited to,” and is not intendedto exclude, for example, other components, integers or steps.“Exemplary” means “an example of” and is not intended to convey anindication of a preferred or ideal embodiment. “Such as” is not used ina restrictive sense, but for explanatory purposes.

Disclosed are components that can be used to perform the disclosedmethods and systems. These and other components are disclosed herein,and it is understood that when combinations, subsets, interactions,groups, etc. of these components are disclosed that while specificreference of each various individual and collective combinations andpermutation of these may not be explicitly disclosed, each isspecifically contemplated and described herein, for all methods andsystems. This applies to all aspects of this application including, butnot limited to, steps in disclosed methods. Thus, if there are a varietyof additional steps that can be performed it is understood that each ofthese additional steps can be performed with any specific embodiment orcombination of embodiments of the disclosed methods.

The present methods and systems may be understood more readily byreference to the following detailed description of preferred embodimentsand the examples included therein and to the Figures and their previousand following description.

As will be appreciated by one skilled in the art, the methods andsystems may take the form of an entirely hardware embodiment, anentirely software embodiment, or an embodiment combining software andhardware aspects. Furthermore, the methods and systems may take the formof a computer program product on a computer-readable storage mediumhaving computer-readable program instructions (e.g., computer software)embodied in the storage medium. More particularly, the present methodsand systems may take the form of web-implemented computer software. Anysuitable computer-readable storage medium may be utilized including harddisks, CD-ROMs, optical storage devices, or magnetic storage devices.

Embodiments of the methods and systems are described below withreference to block diagrams and flowchart illustrations of methods,systems, apparatuses and computer program products. It will beunderstood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, respectively, can be implemented by computerprogram instructions. These computer program instructions may be loadedonto a general purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions which execute on the computer or other programmabledata processing apparatus create a means for implementing the functionsspecified in the flowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide steps for implementing the functions specified in theflowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport combinations of means for performing the specified functions,combinations of steps for performing the specified functions and programinstruction means for performing the specified functions. It will alsobe understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, can be implemented by special purposehardware-based computer systems that perform the specified functions orsteps, or combinations of special purpose hardware and computerinstructions.

As described in greater detail below, in one aspect of the disclosure, asystem can be configured to provide services such as provisioningservice to a user device. FIG. 1 illustrates various aspects of anexemplary environment in which the present methods and systems canoperate. The present disclosure is relevant to systems and methods forproviding services to a user device, for example. Those skilled in theart will appreciate that present methods may be used in various types ofnetworks and systems that employ both digital and analog equipment. Oneskilled in the art will appreciate that provided herein is a functionaldescription and that the respective functions can be performed bysoftware, hardware, or a combination of software and hardware.

The network and system can comprise a user device 102 in communicationwith a computing device 104 such as a server, for example. The computingdevice 104 can be disposed locally or remotely relative to the userdevice 102. As an example, the user device 102 and the computing device104 can be in communication via a private and/or public network 105 suchas the Internet. Other forms of communications can be used such as wiredand wireless telecommunication channels, for example.

In an aspect, the user device 102 can be an electronic device such as acomputer, a smartphone, a laptop, a tablet, a set top box, a displaydevice, or other device capable of communicating with the computingdevice 104. As an example, the user device 102 can comprise acommunication element 106 for providing an interface to a user tointeract with the user device 102 and/or the computing device 104. Thecommunication element 106 can be any interface for presentinginformation to the user and receiving a user feedback such as a webbrowser (e.g., Internet Explorer, Mozilla Firefox, Google Chrome,Safari, or the like). Other software, hardware, and/or interfaces can beused to provide communication between the user and one or more of theuser device 102 and the computing device 104. As an example, thecommunication element 106 can request or query various files from alocal source and/or a remote source. As a further example, thecommunication element 106 can transmit data to a local or remote devicesuch as the computing device 104.

In an aspect, the user device 102 can be associated with a useridentifier or device identifier 108. As an example, the deviceidentifier 108 can be any identifier, token, character, string, or thelike, for differentiating one user or user device (e.g., user device102) from another user or user device. In a further aspect, the deviceidentifier 108 can identify a user or user device as belonging to aparticular class of users or user devices. As a further example, thedevice identifier 108 can comprise information relating to the userdevice such as a manufacturer, a model or type of device, a serviceprovider associated with the user device 102, a state of the user device102, a locator, and/or a label or classifier. Other information can berepresented by the device identifier 108.

In an aspect, the device identifier 108 can comprise an address element110 and a service element 112. In an aspect, the address element 110 canbe an internet protocol address, a network address, an Internet address,or the like. As an example, the address element 110 can be relied uponto establish a communication session between the user device 102 and thecomputing device 104 or other devices and/or networks. As a furtherexample, the address element 110 can be used as an identifier or locatorof the user device 102. In an aspect, the address element 110 can bepersistent for a particular network.

In an aspect, the service element 112 can comprise an identification ofa service provider associated with the user device 102 and/or with theclass of user device 102. As an example, the service element 112 cancomprise information relating to or provided by a communication serviceprovider (e.g., Internet service provider) that is providing or enablingcommunication services to the user device 102. As a further example, theservice element 112 can comprise information relating to a preferredservice provider for one or more particular services relating to theuser device 102. In an aspect, the address element 110 can be used toidentify or retrieve the service element 112, or vise versa. As afurther example, one or more of the address element 110 and the serviceelement 112 can be stored remotely from the user device 102 andretrieved by one or more devices such as the user device 102 and thecomputing device 104. Other information can be represented by theservice element 112.

In an aspect, the computing device 104 can be a server for communicatingwith the user device 102. As an example, the computing device 104 cancommunicate with the user device 102 for providing services. In anaspect, the computing device 104 can allow the user device 102 tointeract with remote resources such as data, devices, and files. As anexample, the computing device can be configured as central location(e.g., a headend, or processing facility), which can receive content(e.g., data, input programming) from multiple sources. The computingdevice 104 can combine the content from the various sources and candistribute the content to user (e.g., subscriber) locations via adistribution system.

In an aspect, the computing device 104 can manage the communicationbetween the user device 102 and a database 114 for sending and receivingdata therebetween. As an example, the database 114 can store a pluralityof files (e.g., web pages), user identifiers or records, or otherinformation. As a further example, the user device 102 can requestand/or retrieve a file from the database 114. In an aspect, the database114 can store information relating to the user device 102 such as theaddress element 110 and/or the service element 112. As an example, thecomputing device 104 can obtain the device identifier 108 from the userdevice 102 and retrieve information from the database 114 such as theaddress element 110 and/or the service elements 112. As a furtherexample, the computing device 104 can obtain the address element 110from the user device 102 and can retrieve the service element 112 fromthe database 114, or vice versa. Any information can be stored in andretrieved from the database 114. The database 114 can be disposedremotely from the computing device 104 and accessed via direct orindirect connection. The database 114 can be integrated with thecomputing system 104 or some other device or system.

In an aspect, one or more access points 116 can be in communication witha network such as network 105. As an example, one or more of the accesspoints 116 can facilitate the connection of a device, such as userdevice 102, to the network 105. As a further example, one or more of theaccess points 116 can be configured as a wireless access point (WAP). Inan aspect, one or more access points 116 can be configured to allow oneor more wireless devices to connect to a wired and/or wireless networkusing Wi-Fi, Bluetooth or similar standard.

In an aspect, the access points 116 can be configured as a mesh network.As an example, one or more access points 116 can comprise a dual bandwireless access point. As an example, the access points 116 can beconfigured with a first service set identifier (SSID) (e.g., associatedwith a user network or private network) to function as a local networkfor a particular user or users. As a further example, the access points116 can be configured with a second service set identifier (SSID) (e.g.,associated with a public/community network or a hidden network) tofunction as a secondary network or redundant network for connectedcommunication devices.

In an aspect, one or more access points 116 can comprise an identifier118. As an example, one or more identifiers can be a media accesscontrol address (MAC address). As a further example, one or moreidentifiers 118 can be a unique identifier for facilitatingcommunications on the physical network segment. In an aspect, each ofthe access points 116 can comprise a distinct identifier 118. As anexample, the identifiers 118 can be associated with a physical locationof the access points 116.

In an aspect, in the OSI reference model, a virtual layer 2 connectioncan be provided to facilitate the connectivity of one or more userdevices 102 and one or more access points 116 of a network. In anaspect, an encapsulation of layer 2 frames over layer 3 networks enablesone or more access points 116 to act as a layer 2 bridge between aclient and a gateway. As an example, a user device 102 can roam betweenthe one or more access points 106 to maintain connectivity to the samenetwork. As a further example, the user device 102 can have a persistentidentifier or address associated therewith while connected to thenetwork.

In an aspect, a layer 3 connection can be provided between one or moreaccess points 116 of the network to facilitate the transmission oflocation information to a gateway or router device of the network. As afurther example, a Generic Routing Encapsulation (GRE) encapsulation canbe used to transmit location information relating to one or more accesspoints connected to the user device.

In an aspect, a network gateway device and/or upstream devices canreceive the location information. As an example, the network gatewaydevice can transmit the location information in authentication andaccounting messages to an authentication, authorization and accounting(AAA) server. As a further example, the AAA server can store and/orupdate the information such as location information in a network sessionstate schema for the located user device 102 when the user device 102moves between access points 116 on the network. In an aspect, sessionstate schema can comprise date/time, calling station identifier, calledstation identifier, Internet Protocol (IP) Address IPV4/IPV6, accountinformation, or other data points.

In an exemplary aspect, the methods and systems can be implemented on acomputing system such as computing device 201 as illustrated in FIG. 2and described below. By way of example, one or more of the user device102 and the computing device 104 of FIG. 1 can be a computer asillustrated in FIG. 2. Similarly, the methods and systems disclosed canutilize one or more computers to perform one or more functions in one ormore locations. FIG. 2 is a block diagram illustrating an exemplaryoperating environment for performing the disclosed methods. Thisexemplary operating environment is only an example of an operatingenvironment and is not intended to suggest any limitation as to thescope of use or functionality of operating environment architecture.Neither should the operating environment be interpreted as having anydependency or requirement relating to any one or combination ofcomponents illustrated in the exemplary operating environment.

The present methods and systems can be operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of well known computing systems, environments,and/or configurations that can be suitable for use with the systems andmethods comprise, but are not limited to, personal computers, servercomputers, laptop devices, and multiprocessor systems. Additionalexamples comprise set top boxes, programmable consumer electronics,network PCs, minicomputers, mainframe computers, distributed computingenvironments that comprise any of the above systems or devices, and thelike.

The processing of the disclosed methods and systems can be performed bysoftware components. The disclosed systems and methods can be describedin the general context of computer-executable instructions, such asprogram modules, being executed by one or more computers or otherdevices. Generally, program modules comprise computer code, routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Thedisclosed methods can also be practiced in grid-based and distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules can be located inboth local and remote computer storage media including memory storagedevices.

Further, one skilled in the art will appreciate that the systems andmethods disclosed herein can be implemented via a general-purposecomputing device in the form of a computing device 201. The componentsof the computing device 201 can comprise, but are not limited to, one ormore processors or processing units 203, a system memory 212, and asystem bus 213 that couples various system components including theprocessor 203 to the system memory 212. In the case of multipleprocessing units 203, the system can utilize parallel computing.

The system bus 213 represents one or more of several possible types ofbus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, sucharchitectures can comprise an Industry Standard Architecture (ISA) bus,a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, aVideo Electronics Standards Association (VESA) local bus, an AcceleratedGraphics Port (AGP) bus, and a Peripheral Component Interconnects (PCI),a PCI-Express bus, a Personal Computer Memory Card Industry Association(PCMCIA), Universal Serial Bus (USB) and the like. The bus 213, and allbuses specified in this description can also be implemented over a wiredor wireless network connection and each of the subsystems, including theprocessor 203, a mass storage device 204, an operating system 205,network software 206, network data 207, a network adapter 208, systemmemory 212, an Input/Output Interface 210, a display adapter 209, adisplay device 211, and a human machine interface 202, can be containedwithin one or more remote computing devices 214 a,b,c at physicallyseparate locations, connected through buses of this form, in effectimplementing a fully distributed system.

The computing device 201 typically comprises a variety of computerreadable media. Exemplary readable media can be any available media thatis accessible by the computing device 201 and comprises, for example andnot meant to be limiting, both volatile and non-volatile media,removable and non-removable media. The system memory 212 comprisescomputer readable media in the form of volatile memory, such as randomaccess memory (RAM), and/or non-volatile memory, such as read onlymemory (ROM). The system memory 212 typically contains data such asnetwork data 207 and/or program modules such as operating system 205 andnetwork software 206 that are immediately accessible to and/or arepresently operated on by the processing unit 203.

In another aspect, the computing device 201 can also comprise otherremovable/non-removable, volatile/non-volatile computer storage media.By way of example, FIG. 2 illustrates a mass storage device 204 whichcan provide non-volatile storage of computer code, computer readableinstructions, data structures, program modules, and other data for thecomputing device 201. For example and not meant to be limiting, a massstorage device 204 can be a hard disk, a removable magnetic disk, aremovable optical disk, magnetic cassettes or other magnetic storagedevices, flash memory cards, CD-ROM, digital versatile disks (DVD) orother optical storage, random access memories (RAM), read only memories(ROM), electrically erasable programmable read-only memory (EEPROM), andthe like.

Optionally, any number of program modules can be stored on the massstorage device 204, including by way of example, an operating system 205and network software 206. Each of the operating system 205 and networksoftware 206 (or some combination thereof) can comprise elements of theprogramming and the network software 206. Network data 207 can also bestored on the mass storage device 204. Network data 207 can be stored inany of one or more databases known in the art. Examples of suchdatabases comprise, DB2®, Microsoft® Access, Microsoft® SQL Server,Oracle@, mySQL, PostgreSQL, and the like. The databases can becentralized or distributed across multiple systems.

In another aspect, the user can enter commands and information into thecomputing device 201 via an input device (not shown). Examples of suchinput devices comprise, but are not limited to, a keyboard, pointingdevice (e.g., a “mouse”), a microphone, a joystick, a scanner, tactileinput devices such as gloves, and other body coverings, and the likeThese and other input devices can be connected to the processing unit203 via a human machine interface 202 that is coupled to the system bus213, but can be connected by other interface and bus structures, such asa parallel port, game port, an IEEE 1394 Port (also known as a Firewireport), a serial port, or a universal serial bus (USB).

In yet another aspect, a display device 211 can also be connected to thesystem bus 213 via an interface, such as a display adapter 209. It iscontemplated that the computing device 201 can have more than onedisplay adapter 209 and the computer 201 can have more than one displaydevice 211. For example, a display device can be a monitor, an LCD(Liquid Crystal Display), or a projector. In addition to the displaydevice 211, other output peripheral devices can comprise components suchas speakers (not shown) and a printer (not shown) which can be connectedto the computing device 201 via Input/Output Interface 210. Any stepand/or result of the methods can be output in any form to an outputdevice. Such output can be any form of visual representation, including,but not limited to, textual, graphical, animation, audio, tactile, andthe like. The display 211 and computing device 201 can be part of onedevice, or separate devices.

The computing device 201 can operate in a networked environment usinglogical connections to one or more remote computing devices 214 a,b,c.By way of example, a remote computing device can be a personal computer,portable computer, a smart phone, a server, a router, a networkcomputer, a peer device or other common network node, and so on. Logicalconnections between the computing device 201 and a remote computingdevice 214 a,b,c can be made via a network 215, such as a local areanetwork (LAN) and a general wide area network (WAN). Such networkconnections can be through a network adapter 208. A network adapter 208can be implemented in both wired and wireless environments. Suchnetworking environments are conventional and commonplace in dwellings,offices, enterprise-wide computer networks, intranets, and the Internet.

For purposes of illustration, application programs and other executableprogram components such as the operating system 205 are illustratedherein as discrete blocks, although it is recognized that such programsand components reside at various times in different storage componentsof the computing device 201, and are executed by the data processor(s)of the computer. An implementation of network software 206 can be storedon or transmitted across some form of computer readable media. Any ofthe disclosed methods can be performed by computer readable instructionsembodied on computer readable media. Computer readable media can be anyavailable media that can be accessed by a computer. By way of exampleand not meant to be limiting, computer readable media can comprise“computer storage media” and “communications media.” “Computer storagemedia” comprise volatile and non-volatile, removable and non-removablemedia implemented in any methods or technology for storage ofinformation such as computer readable instructions, data structures,program modules, or other data. Exemplary computer storage mediacomprises, but is not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed by acomputer.

The methods and systems can employ Artificial Intelligence techniquessuch as machine learning and iterative learning. Examples of suchtechniques include, but are not limited to, expert systems, case basedreasoning, Bayesian networks, behavior based AI, neural networks, fuzzysystems, evolutionary computation (e.g. genetic algorithms), swarmintelligence (e.g. ant algorithms), and hybrid intelligent systems (e.g.expert inference rules generated through a neural network or productionrules from statistical learning).

FIGS. 3-4 illustrate an exemplary system and network. In an aspect, aplurality of nodes 302 can be in communication with one or more userdevices 303 and one or more computing devices 304. As an example, one ormore nodes can be a network access point, router, switch, communicationdevice, or the like. As another example, one or more user devices 303can be an electronic device such as a computer, a smartphone, a laptop,a tablet, a set top box, a display device, or other device capable ofcommunicating with one or more of the nodes 302 of the network. As afurther example, one or more of the computing devices 304 can be agateway, router, switch, communication device terminal server, cablemodem termination system, and the like.

In an aspect, one or more of the nodes 302 can be configured tocommunicate with another of the nodes 302 and/or one or more of thecomputing devices 304 via one or more communication paths 306. In anaspect, the one or more communication paths 306 can comprise one or moreuninterrupted communication links, sequential links, pre-defined pathsor links, and/or intervening nodes. Links can comprise a single point topoint connection between two devices or access points. Paths cancomprise one or more links. As an example, one or more of thecommunication paths can comprise one or more of the nodes 302. As afurther example, one or more of the nodes 302 can be configured as amesh network. In an aspect, one ore more of the communication paths 306can be configured to transmit one or more services.

In an aspect, one or more of the nodes 302 can comprise an identifier308. As an example, one or more identifiers can be a media accesscontrol address (MAC address). Any uniquely identifiable attribute thatcan be linked to a location can be used as the identifier 308. Suchattributes can comprise one or more of an IP Address, serial number,latitude/longitude, geo-encoding, custom assigned unique identifier,global unique identifier (GUID), and the like. As a further example, oneor more identifiers 308 can be a unique identifier for facilitatingcommunications on the physical network segment. In an aspect, each ofthe nodes 302 can comprise a distinct identifier 308. As an example, theidentifiers 308 can be associated with a physical location of the nodes302.

In an aspect, an AAA server 310 can be in communication with thecomputing device 304. The AAA server 310 can comprise securityarchitecture for the network of nodes 302 or other distributed systems.As an example, the AAA server 310 can control which user devices (e.g.,user device 303) are allowed access to which services. As a furtherexample, the AAA server 310 can control the resources available to thenetwork of nodes 302. In an aspect, the AAA server 310 can communicatevia one or more network protocols such as the RADIUS protocol or theDiameter protocol, for example.

As shown in FIG. 3, when the user device 303 connects to a first node302′ of the network of nodes 302, a first identifier 308′ associatedwith the first node 302′ can be detected. In an aspect, the firstidentifier 308′ can be detected using dynamic host configurationprotocol (DHCP). As an example, a DHCP discover option (e.g., option 82)can be used to transmit the first identifier 308′ to the gateway 304. Asa further example, a DHCP option can be used to allocate addresselements such as IP addresses to the user device.

As shown in FIG. 4, when the user device 303 moves from the first node302′ and connects to a second node 302″ of the network of nodes 302, asecond identifier 308″ associated with the second node 302″ can bedetected. In an aspect, data transfer between the user device 303 andthe second node 302″ can define a triggering event. As an example, thesecond identifier 308″ can be transmitted to a routing device such asthe network gateway 304. As a further example, the second identifier308″ can be transmitted in response to the triggering event. In anaspect, the second identifier 308″ can be encapsulated for transmissionsuch as by GRE encapsulation. In an aspect, the user device 303 may notbe required to issue a DHCP request when the user device 303 connects toanother node 302 having the same SSID. In particular, the user device302 operates substantially as if it is part of the same layer 2 network.Accordingly, since a DHCP request is not required, the current IPaddress assigned to the user device 303 should still be valid on thenetwork. As an example, the second identifier can be transmitted to amanagement device such as an AAA server 310. As a further example, themanagement device can be configured to control an operation of one ormore of the second node 302″ and the gateway 304 in response to theidentifier.

In an aspect, provided are methods for managing location information ina network. An exemplary method is shown in FIG. 5. The methodillustrated in FIG. 5 will be discussed, for example only, in referenceto FIGS. 1-4. In step 502, a triggering event can be detected. In anaspect, the triggering event can be detected at one or more nodes 302(FIGS. 3-4). As an example, the triggering event can comprise receivingdata at one or more nodes 302. As a further example, the triggeringevent can comprise a communication between one or more nodes 302 and aconnected device (e.g., user device 303 or a client).

In step 504, location information can be transmitted to a routing devicesuch as gateway 304 (FIGS. 3-4). In an aspect, the location informationcan be associated with one or more nodes 302. As an example, thelocation information can be transmitted in response to the triggeringevent of step 502. As a further example, the location information cancomprise an identifier such as a MAC address associated with one of thenodes 302. In an aspect, the location information can be encapsulated(e.g., GRE encapsulation) for transmission. As an example, the locationinformation can be encapsulated using one or more of an internet controlmessaging protocol, address resolution protocol, and connectivity faultmanagement protocol. Other protocols and encapsulation can be used.

In step 506, the location information can be transmitted to a managementdevice such as the AAA server 310 (FIGS. 3-4). In an aspect, themanagement device can be configured to control an operation of one ormore of the nodes and the routing device in response to the locationinformation. In an aspect, transmitting location information oridentifiers to a management device is executed by the routing device.

In an aspect, provided are methods for managing location information ina network. An exemplary method is shown in FIG. 6. The methodillustrated in FIG. 6 will be discussed, for example only, in referenceto FIGS. 1-4. In step 602, location information can be received, forexample, at a routing device such as gateway 304 (FIGS. 3-4). In anaspect, the location information can be associated with one or morenodes 302. As an example, the location information can be transmitted inresponse to the triggering event of step 502. As a further example, thelocation information can comprise an identifier such as a MAC addressassociated with one of the nodes 302. In an aspect, the locationinformation can be encapsulated (e.g., GRE encapsulation) fortransmission. As an example, the location information can beencapsulated using one or more of an internet control messagingprotocol, address resolution protocol, and connectivity fault managementprotocol. Other protocols and encapsulation can be used.

In step 604, the location information can be transmitted to a managementdevice such as the AAA server 310 (FIGS. 3-4). As an example, therouting device can transmit the location information to the managementdevice. As a further example, the location information can betransmitted to the management device in an unencapsulated format. In anaspect, the management device can be configured to control an operationof one or more of the nodes and the routing device in response to thelocation information. In an aspect, transmitting location information oridentifiers to a management device is executed by the routing device.

In step 606, the management device can control the operation of one ormore of the routing device, a node, and/or a user device based on thelocation information. In an aspect, controlling one or more of therouting device, a node, and/or a user device can comprise provisioningthe same.

In an aspect, FIG. 7 illustrates an exemplary method for managing anetwork. The method illustrated in FIG. 7 will be discussed, for exampleonly, in reference to FIGS. 1-4. In step 702, first location informationcan be received. In an aspect, the first location information cancomprise an identifier such as a MAC address. As an example, the firstlocation information can be received from and/or related to one or morenodes of a network. As a further example, the location information canbe received based upon a user communication with a first node of anetwork.

In step 704, second location information can be received. In an aspect,the second location information can comprise an identifier such as a MACaddress. As an example, the second location information can be receivedfrom and/or related to one or more nodes of a network. As a furtherexample, the location information can be received based upon a usercommunication with a second node of a network. In an aspect, the secondlocation information can be received in an encapsulated format. As anexample, the second location information can be encapsulated usinggeneric routing encapsulation. As a further example, the second locationinformation can be encapsulated using one or more of internet controlmessaging protocol, address resolution protocol, and connectivity faultmanagement protocol.

In step 706, a client location data can be stored or updated. In anaspect, the client location data can comprise one or more of the firstlocation information and the second location information. As an example,the client location data can be updated based on one or more of thefirst location information and the second location information. As afurther example, the AAA server can store and/or update the locationvalue in a network session state for the located user device when theuser device moves between access points on the network. In an aspect,session schema can comprise contain date/time, calling stationidentifier, called station identifier, Internet Protocol (IP) AddressIPV4/IPV6, account, or other data points.

In an aspect, location awareness of user devices connected to a network(e.g., a wireless LAN, open WiFi network, or the like) can facilitateproviding co-branded login pages, user interfaces or advertisementsspecific to the AP location through which one or more user devices areconnected to the network. As an example, services/features can beprovided at specific locations (e.g. amenity or guest services) and tospecific user devices connected at those locations. As a furtherexample, understanding traffic demographics can assist in targeting anddeveloping future AP deployments for the network. In an aspect, policiessuch as WiFi Channel, WiFi Band (2.4 or 5 GHZ) or SSID Steering orPreference can be supplied based upon knowledge of client deviceidentity at a given access point or node location to help provideoptimal service. As an example, home users to can be steered to aprivate SSID when they are at their home location.

While the methods and systems have been described in connection withpreferred embodiments and specific examples, it is not intended that thescope be limited to the particular embodiments set forth, as theembodiments herein are intended in all respects to be illustrativerather than restrictive.

Unless otherwise expressly stated, it is in no way intended that anymethod set forth herein be construed as requiring that its steps beperformed in a specific order. Accordingly, where a method claim doesnot actually recite an order to be followed by its steps or it is nototherwise specifically stated in the claims or descriptions that thesteps are to be limited to a specific order, it is no way intended thatan order be inferred, in any respect. This holds for any possiblenon-express basis for interpretation, including: matters of logic withrespect to arrangement of steps or operational flow; plain meaningderived from grammatical organization or punctuation; the number or typeof embodiments described in the specification.

It will be apparent to those skilled in the art that variousmodifications and variations can be made without departing from thescope or spirit. Other embodiments will be apparent to those skilled inthe art from consideration of the specification and practice disclosedherein. It is intended that the specification and examples be consideredas exemplary only, with a true scope and spirit being indicated by thefollowing claims.

What is claimed is:
 1. A system comprising: an access point, configuredto: detect a triggering event, wherein the triggering event comprises acommunication between the access point and a user device, encapsulate,based on the triggering event and using generic routing encapsulation, alayer 2 frame within a layer 3 packet, wherein the layer 2 framecomprises an identifier of the access point, and wherein the identifieris associated with a location of the access point, send, to a routingdevice based on the triggering event, the encapsulated identifier;wherein the routing device is configured to: receive the encapsulatedidentifier, and send, to a management device, the encapsulatedidentifier; and wherein the management device is configured to: receivethe encapsulated identifier, and control, based on the encapsulatedidentifier, an operation of one or more of the access point or therouting device.
 2. The system of claim 1, wherein the communicationbetween the access point and the user device comprises one or more datapackets received by the access point from the user device.
 3. The systemof claim 1, wherein the identifier comprises a Media Access Control(MAC) address associated with the access point.
 4. The method of claim1, wherein the access point is further configured to encapsulate theidentifier in the layer 2 frame based on one or more of internet controlmessaging protocol, address resolution protocol, or connectivity faultmanagement protocol.
 5. The system of claim 1, wherein the access pointcomprises one or more of a wireless router or a gateway device.
 6. Thesystem of claim 1, wherein the management device comprises one or moreof an authentication element, an authorization element, or an accountingelement.
 7. A method comprising: receiving, by a routing device, basedon a first communication between a first access point and a user device,a first identifier of the first access point, wherein the firstidentifier is associated with a location of the first access point;receiving, based on a second communication between a second access pointand the user device, a second identifier of the second access point,wherein the second identifier is associated with a location of thesecond access point, and wherein the second identifier is received in alayer 2 frame, wherein the layer 2 frame is encapsulated, based ongeneric routing encapsulation, in a layer 3 packet by the second accesspoint; determining, based on the second identifier, location dataassociated with the user device; and causing, based on the locationdata, one or more advertisements to be sent to the user device.
 8. Themethod of claim 7, wherein the first identifier comprises a Media AccessControl (MAC) address associated with the first access point, andwherein the second identifier comprises a MAC address associated withthe second access point.
 9. The method of claim 7, wherein the secondidentifier is encapsulated in the layer 2 frame using one or more ofinternet control messaging protocol, address resolution protocol, orconnectivity fault management protocol.
 10. The method of claim 7,wherein one or more of the first access point or the second access pointcomprises one or more of a wireless router or a gateway device.
 11. Themethod of claim 7, further comprising sending, to a management device,the second identifier, wherein the management device comprises one ormore of an authentication element, an authorization element, or anaccounting element.
 12. The method of claim 7, wherein causing the oneor more advertisements to be sent to the user device comprises causing amanagement device to send the one or more advertisements.
 13. A methodcomprising: determining, by a routing device, based on a firstidentifier of a first access point, a location of a user device, whereinthe first identifier is associated with a location of the first accesspoint; receiving, based on a communication between a second access pointand the user device, a second identifier of the second access point,wherein the second identifier is associated with a location of thesecond access point, and wherein the second identifier is received in alayer 2 frame, wherein the layer 2 frame is encapsulated, based ongeneric routing encapsulation, in a layer 3 packet by the second accesspoint; and updating, based on the second identifier, the location of theuser device.
 14. The method of claim 13, wherein the first identifier isreceived based on a communication between the first access point and theuser device.
 15. The method of claim 13, wherein the first identifiercomprises a Media Access Control (MAC) address associated with the firstaccess point, and wherein the second identifier comprises a MAC addressassociated with the second access point.
 16. The method of claim 13,wherein the second identifier is encapsulated in the layer 2 frame usingone or more of internet control messaging protocol, address resolutionprotocol, or connectivity fault management protocol.
 17. The method ofclaim 13, wherein one or more of the first access point or the secondaccess point comprises one or more of a wireless router or a gatewaydevice.
 18. The method of claim 13, further comprising sending, to amanagement device, the second identifier, wherein the management devicecomprises one or more of an authentication element, an authorizationelement, or an accounting element.
 19. The method of 13, furthercomprising causing, based on the updated location of the user device,one or more advertisements to be sent to the user device.
 20. The methodof claim 19, wherein causing the one or more advertisements to be sentto the user device comprises causing a management device to send the oneor more advertisements.
 21. One or more non-transitory computer readablemedia storing processor executable instructions that, when executed byat least one processor, cause the at least one processor to: detect atriggering event, wherein the triggering event comprises a communicationbetween an access point and a user device; encapsulate, based on thetriggering event and using generic routing encapsulation, a layer 2frame within a layer 3 packet, wherein the layer 2 frame comprises anidentifier of the access point, and wherein the identifier is associatedwith a location of the access point; send, to a routing device based onthe triggering event, the encapsulated identifier; and cause atransmission of the encapsulated identifier of the access point to amanagement device by the routing device, wherein the management deviceis configured to control, based on the encapsulated identifier, anoperation of one or more of the access point and the routing device inresponse to the identifier.
 22. The one or more non-transitory computerreadable media of claim 21, wherein the communication between the accesspoint and the user device comprises one or more data packets received bythe access point from the user device.
 23. The one or morenon-transitory computer readable media of claim 21, wherein theidentifier comprises a Media Access Control (MAC) address associatedwith the access point.
 24. The one or more non-transitory computerreadable media of claim 21, wherein the processor executableinstructions, when executed by the at least one processor, further causethe at least one processor to encapsulate the identifier in the layer 2frame based on one or more of internet control messaging protocol,address resolution protocol, or connectivity fault management protocol.25. The one or more non-transitory computer readable media of claim 21,wherein the access point comprises one or more of a wireless router or agateway device.
 26. The one or more non-transitory computer readablemedia of claim 21, wherein the management device comprises one or moreof an authentication element, an authorization element, or an accountingelement.